ci(release): add tag-triggered release workflow#72
Merged
Conversation
release.yml fires on vX.Y.Z tag pushes: it re-runs `mvnw clean verify -pl .` against the tagged commit as a green-build gate, then creates (or updates) a GitHub Release whose body is that version's CHANGELOG section. Pre-release tags (e.g. v1.7.0-rc.1) ship as GitHub pre-releases. Removes the manual "create a GitHub Release" step from the release checklist. The version-consistency guard passes by construction because cut-release.ps1 bumps every version site in the release commit (#71).
DemchaAV
added a commit
that referenced
this pull request
May 29, 2026
…ase.yml (#74) Updates the release runbook to match the v1.6.5 plumbing (#69 #70 #71 #72 #73): - README install snippets now flip in the release commit (cut-release.ps1), enforced by VersionConsistencyGuardTest — replaces the old "stay pinned to the previous tag, flip post-release" model that contradicted the guard. - Version lives in four sites (library pom, aggregator, inherited examples/benchmarks parents); the script bumps all four + README in one pass. - GitHub Release is created automatically by release.yml on tag push; the manual gh release create is now the documented fallback. - Adds VersionConsistencyGuardTest to the pre-release guard-suite gate, and a v1.6.5 lesson that supersedes the v1.6.0 graphcompose.version property note. The graphcompose-release-engineer skill (local config, Claude + Codex copies) was aligned in lockstep.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/release.yml, triggered onv*tag pushes.mvnw clean verify -pl .on the tagged commit as a green-build gate, then creates/updates a GitHub Release with that version's CHANGELOG section as the body.v1.7.0-rc.1) ship as GitHub pre-releases. Idempotent — edits the notes if the release already exists.Why
Tag pushes previously triggered nothing; the GitHub Release was a manual step. This automates it and guarantees a tag only ships if the build is green. The version guard (#70) passes by construction since cut-release.ps1 (#71) bumps every version site in the release commit.
Test plan
Note
permissions: contents: writeis scoped to this workflow only; CI stayscontents: read.